Peer to peer communications for repairing wireless multicast/broadcast delivered content

ABSTRACT

A method for repairing multicast/broadcast content via peer to peer communications, which includes receiving at least a part of a file transmitted by a wireless multicast/broadcast service (WMBS) session via an access network; exchanging, via a peer to peer network, completion messages between the UE device and peer UE devices upon completion of the WMBS session; identifying an amount of the file received at the UE device, and amounts of the file received at each of peer UE devices based on the exchanged completion messages; sending repair data to repair the file on each peer UE devices in response to identifying that the UE device received the entire file; and sending repair data via the peer to peer network, obtained from the access network, in response to identifying that the UE device received less than the entire file and more of the file than each of the group of peer UE devices.

BACKGROUND

A wireless multicast/broadcast service (WMBS) is a point-to-multipointservice in which data is wirelessly transmitted from a source tomultiple destinations. For example, in a long term evolution (LTE)system, one WMBS based on 3GPP is the enhanced multimedia broadcastmulticast services (eMBMS). The WMBS is designed to provide varioustypes of content to end devices using broadcast and multicast deliverymethods. In some instances, end devices may not receive complete datasets over a WMBS which may result in incomplete files. Conventionaltechniques to repair incomplete files should occur within a limited timewindow, and may result in excess bandwidth consumption, increased costs,and/or excess loads on network components.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B are diagrams showing an exemplary environment associatedwith repairing WMBS content using peer to peer communications;

FIG. 2 is a block diagram showing an exemplary networking environmentfor repairing WMBS content using peer to peer communications accordingto an embodiment;

FIG. 3 is a block diagram illustrating an exemplary Long Term Evolution(LTE) networking environment according to an embodiment;

FIG. 4 is a block diagram showing exemplary components of a userequipment device according to an embodiment;

FIG. 5 is a flow diagram showing exemplary process blocks and signalflows for initiating a file repair via a wireless peer to peer network;

FIG. 6 is a flow diagram showing exemplary process blocks and signalflows for performing a seed mode file repair via a wireless peer to peernetwork;

FIG. 7 is a flow diagram showing exemplary process blocks and signalflows for performing a lead mode file repair via a wireless peer to peernetwork; and

FIG. 8 is a flow chart showing an exemplary process for repairing WMBSsession data via a peer to peer network.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. The following detailed description does not limitthe invention.

Embodiments described herein are directed to peer to peer mechanisms forrepairing content delivered over wireless multicast/broadcast service(WMBS). As used herein, the term WMBS is broadly defined as acommunication service that may transmit in a multicast mode (one tomultiple end devices in a service area) and/or a broadcast mode (one toall end devices in a service area) via a wireless network. WMBS providesan efficient mechanism to deliver common content over the wirelessnetwork which may be directed to targeted areas which are referred toherein as WMBS service areas.

At the conclusion of a WMBS session, end devices may not receive theentire file as intended. Situational and/or environmental conditions mayprevent end devices from receiving the entire (100%) of the file. Forexample, end devices being located in buildings or structures whichattenuate radio frequency (RF) signals may result in only partial filesbeing received. Other obstructions based on topology and/or occludingobjects can also impede reception. In other situations, problems withthe end device may prevent full reception. Existing standards (e.g.,3GPP TS 26.346) provide conventional mechanisms to enable the repair ofan incomplete file received over a WMBS session on an end device. Theconventional mechanisms are based on unicast transmission from thenetwork to retrieve the data required to complete the missing files onthe end devices. The conventional file repair mechanisms are timesensitive, thus end devices must tune in precisely within a very shorttime window at the end of a WMBS session to download symbols before datarepresenting the file is purged from the WMBS platform facilitating thesession. Moreover, conventional file repair systems may not limit thenumber of end devices which may simultaneously attempt to contact theWMBS platform. Two of the conventional file repair mechanisms aredescribed below in more detail.

A first conventional mechanism is known as “byte range file repair,”where end devices may download missing symbols representing the datafile directly from a content distribution network (CDN) over a unicastsession. With byte range file repair, a unicast session may beestablished between the end device and the CDN based on metadata in theassociative data function (APD) fragment. Disadvantages to byte rangefile repair may include: 1) increased costs, as calls to the CDN incurcharges; 2) excess bandwidth consumption as end devices compete toperform unicast file repair; 3) time constraints for obtaining missingsymbols due to the CDN only storing the file for a limited time, and thestandard only allowing unicast connections for repair a short time afterthe WMBS session has ended; and 4) performance and/or availability forrepair may be contingent on CN load balancing performance.

A second conventional mechanism is known as “conventional file repair,”where end devices may download missing symbols representing the datafile from the WMBS platform over a unicast session via a network. In anembodiment, an end device may establish a unicast connection with anassociative data function (ADF) within a broadcast multicast servicecenter (BMSC)). Disadvantages to conventional file repair mayinclude: 1) excess bandwidth consumption as end devices compete toperform unicast file repair; 2) time constraints for obtaining missingsymbols due to the standard only allowing unicast connections for repaira short time after the WMBS session has ended; and 3) request from alarge number of end devices may overload the BMSC.

Despite the provisions provided by the conventional file repairmechanisms, some end devices may be unable to complete the filedownload. Accordingly, embodiments herein provide approaches tocircumvent each end point device having to repair files over a unicastconnection with the network. Instead, end point devices may form a peerto peer network and exchange symbols with proximate end devices toobtain missing symbols for incomplete file downloads. Using peer to peercommunications to facilitate file repair may reduce the amount ofnetwork bandwidth consumption for the file repair, alleviate the timeconstraints of conventional methods, avoid overloading networkcomponents such as the BMSC, and improving the reliability of the filerepair to each end device.

FIGS. 1A and 1B are diagrams showing an exemplary environment 100associated with repairing wireless multicast/broadcast service (WMBS)content using peer to peer communications. Environment 100 may includean WMBS service area 110, mobile devices 120 (herein referred toplurally as “mobile devices 120,” generically as “mobile device 120,”and individually as “mobile device 120-x”), base station 130, WMBSplatform 140, and content delivery network (CDN) 150.

In environment 100, one or more base stations 130 may establish WMBSservice area 110 by providing coordinated transmissions for reception bymobile devices 120 located within WMBS service area 110. WMBStransmissions may be sent over a cellular wireless network, indicated assolid arrows emanating from base station 130 in FIGS. 1A and 1B. TheWMBS transmission may be provided using a simulcast technique that sendssimilar waveforms at substantially the same time from one or more basestations (only one base station 130 is shown in FIGS. 1A and 1B forsimplicity). WMBS embodiments presented herein may be implemented usingany type of wireless communication standard, such as, for example inlong term evolution (LTE) wireless networks (e.g., LTE, LTE Advanced,etc.) using WMBS standards such as the evolved Multimedia BroadcastMulticast System (eMBMS) standard. Alternatively, embodiments herein areapplicable to wireless multicast/broadcast services in the upcoming 5Gnew radio (NR) wireless standards.

Content may be stored in CDN 150 in the form of files. WMBS platform 140may receive files from CDN 150 and provide them to base station 130,where the files may be efficiently distributed to mobile devices 120 inWMBS service area 110 via multicast or broadcast. During the WMBSservice, each mobile device 120 monitors the WMBS transmission from basestation 130 to estimate when the end time of the WMBS transmissionoccurs. Mobile devices 120 may monitor, for example, the file sizeand/or the transmission bandwidth associated with the WMBS service.Mobile devices 120 may recalculate the end time for verification,because a short time window (e.g., 30 seconds) for establishing filerepair may be enforced by WMBS platform 140. Once the WMBS session iscomplete, mobile devices 120 may start a time to ensure file isinitiated within the short time window, and each mobile device 120 maydetermine how much of the file was received, and then broadcast acompletion message to peer mobile devices 120. The completion messagemay include a mobile device name/identifier, a file name identifying thecontent received, and a completion status. The completion status mayindicate how much of file was received from base station 130. A mobiledevice 120-x may compare the amount of the file received with theamounts received by peer mobile devices 120.

In instances where one or more mobile devices 120 fail to receive anentire file transmitted by base station 130, the files may be “repaired”via a peer to peer network using two different modes of repair: one typeof repair is referred to herein as “seed mode” repair, and the othertype of repair referred to as “lead mode” repair.

FIG. 1A is a diagram showing an example where seed mode file repair isperformed within exemplary environment 100. If one or more mobiledevices 120 report, via the received completion messages, receiving theentire file, the mobile device(s) 120 determine that received the entirefile may be designated as a “seed mobile device.” As shown in FIG. 1A,mobile device 120-1 received 100% of the file from base station 130, andis thus designated as the seed mobile device. Once designated, seedmobile device 120-1 may generate a prioritized list of peer mobiledevices 120 that may be contacted by seed mobile device 120-1 via thepeer to peer network (shown in FIGS. 1A and 1B as dashed arrows). Theprioritized list generated by mobile device 120-1 may be prioritizedusing an algorithm, which may sort the nearby mobile devices 120 into aqueue based on, for example, proximity, wireless channel strength of thepeer to peer network with respect to each peer mobile device 120 (i.e.,the wireless device-to-device signal strength, such as the wirelesssignal strength between seed mobile device 120-1 and each peer mobiledevice(s) 120), and/or the fraction of the file received by peer mobiledevices 120. As shown in FIG. 1A, peer mobile devices 120 are shown inorder of the prioritized queue as mobile devices 120-2 through 120-5,based on the percentage of the file received/stored, where largerpercentages are given higher priority. Seed mobile device 120-1 maybroadcast over the peer to peer network the prioritized list so thatpeer mobile devices 120-2 through 120-5 receive the queue priority.Additionally, seed mobile device 120-1 may determine a maximum number ofallowed simultaneous connections for file repair, which may be set as aconfigurable parameter on each mobile device 120.

As shown in FIG. 1A, seed mobile device 120-1 may initially providerepair data to mobile device 120-2 (indicated as peer to peer repair andlabeled “1”), and then mobile device 120-3 (indicated as peer to peerrepair and labeled “2”). Once devices 120-2 and 120-3 receive enoughrepair data from seed mobile device 120-1 to complete the file, mobiledevice 120-2 and mobile device 120-3 may transition into seed mode torepair other peer mobile devices further down in the prioritized queue.For example, as shown in FIG. 1A, mobile device 120-2 may provide repairdata to mobile device 120-4 (indicated as peer to peer repair andlabeled “3”), using the repaired file data received from mobile device120-1, and mobile device 120-3 may provide repair data to mobile device120-5 (indicated as peer to peer repair and labeled “4”). The peer topeer repair process concludes once all of the peer mobile devices 120-2through 120-5 have received and stored the entire file.

FIG. 1B is a diagram showing an example where lead mode file repair isperformed within exemplary environment 100. In this example, when all ofthe mobile devices 120 report, via completion messages, of receivingless than the entire file, mobile devices 120 may determine the mobiledevice 120-i having the largest amount of the file. For example, asshown in FIG. 1B, mobile device 120-1 received 99% of the file, and isthus designated by mobile devices 120, based on the completion messages,as the “lead device.” Once so designated, lead mobile device 120-1 mayinitiate a unicast session with the network to download repair data andcomplete the file stored on mobile device 120-1. The unicast session maybe undertaken as a conventional byte file repair, in which lead mobiledevice 120-1 receives repair data from WMBS platform 140. Alternatively,the unicast session may be undertaken as a byte range file repair, wheremobile device 120 receives repair data from CDN 150. Whether mobiledevice 120-1 chooses byte range file repair or conventional file repairmay be based upon the amount of data required to repair the file, thecosts incurred repairing the file through CDN 150, and the availabilityof repair data.

Once lead mobile device 120-1 has the entire file, mobile device 120-1may transition into seed mode as described above in FIG. 1A.Accordingly, newly designated seed mode device 120-1 may generate aprioritized queue for peer mobile devices 120-2 through 120-5, andproceed to send repair data to peer mobile devices 120-2 through 120-5based on the prioritized queue as described above in FIG. 1A. By onlycontacting the network with one device (e.g., mobile device 120-1 inFIG. 1B), and having the remaining peer devices 120 use the peer to peernetwork to obtain the repair data, the connections to the network can besignificantly reduced which may lower content cost and reduce networkbandwidth consumption, and prevent overloading devices in the WMBSplatform 140 and/or CDN 150.

FIG. 2 is a block diagram showing an exemplary networking environment200 for repairing WMBS content using peer to peer communicationsaccording to an embodiment. The environment may include a mobile device120, networks 230, WMBS platform 140, and content delivery network 150.For ease of explanation, only one mobile device 120 is illustrated asbeing connected to networks 230. However, it should be understood that aplurality of mobile devices 120, may be communicatively coupled tonetworks 230.

Networks 230 may include a plurality of networks of any type, and may bebroadly grouped into one or more access network(s) 230-1 and one or moreback end network(s) 230-2. Access network(s) 230-1 provides connectivitybetween mobile device 120 and other network elements within accessnetwork(s) 230-1 and/or back end network(s) 230-2. Access network(s)230-1 may include, for example, a telecommunications network (e.g., aPublic Switched Telephone Network (PSTN)), wired (e.g., Ethernet) and/orwireless local area network(s) (LAN) (e.g., WiFi), wireless wide areanetworks (WAN) (e.g., WiMax), and/or one or more wireless public landmobile networks (PLMNs). The PLMN(s) may include a Code DivisionMultiple Access (CDMA) 2000 PLMN, a Global System for MobileCommunications (GSM) PLMN, a Long Term Evolution (e.g., LTE, LTEAdvanced) PLMN, a 5G new radio (NR) PLMN and/or other types of PLMNs notspecifically described herein. In other embodiments, access network(s)230-1 may alternatively or additionally include any type of Wi-Fi (e.g.,any IEEE 801.11x network, where x=a, b, c, g, and/or n). A wide areawireless network may include any type of wireless network coveringlarger areas, and may include a mesh network (e.g., IEEE 801.11s) and/oror a WiMAX IEEE 802.16.

Back end network(s) 230-2 may exchange data with access network(s) 230-1to provide mobile device 120 connectivity to various servers, gateways,and other network entities, which may include one or more CDNs 150. Backend network(s) 230-2 may include a wide area network (WAN), ametropolitan area network (MAN), an intranet, the Internet, a wirelesssatellite network, a cable network (e.g., an optical cable network).

Mobile device 120 may include any type of electronic device havingcommunication capabilities, and thus communicate over networks 230 usinga variety of different channels, including both wired and wirelessconnections. Mobile device 120 may include, for example, a cellularradiotelephone, a smart phone, a tablet, a set-top box (STB), a mobilephone, a Voice over Internet Protocol (VoIP) device, a laptop computer,a palmtop computer, a gaming device, a wearable computer (e.g., a smartwatch, eye glasses, etc.), a media player device, or a digital camerathat includes communication capabilities (e.g., wireless communicationmechanisms). Mobile device 120 may be embedded in other types ofdevices, such as, for example, enterprise devices such as cashregisters, appliances, cameras, digital signs, point of sale terminals;and any type of vehicle used for transportation such as cars, ships,aircraft, golf carts, etc. Mobile device 120 may also be referred to asa “User Equipment” (UE) device when discussed in context with LTE and/orLTE Advanced wireless networks.

Mobile device 120 may further include software for facilitating WMBSoperations, including a mobile connected media—middleware (MCM-MW) 215and a repair manager 217, for facilitating reception and file repair ofWMBS content. MCM-MW 215 may control the modem of mobile device 120 andprovide functionality for tuning and for unicast file repair of WMBSreceived content. Repair manager 217 may operate in conjunction withMCM-MW 215 to facilitate file repair between mobile devices 120 overpeer to peer networks.

Further referring to FIG. 2, WMBS platform 140 may interface with accessnetwork 230-1 and back end networks 230-2 to exchange content data withCDN 150. WMBS platform 140 may include broadcast video provisioningsystem (BVPS) 240, and broadcast multicast service control/associativedata function (BMSC/ADF) 250. BVPS 240 include one or more computationand/or communication devices that may manage WMBS sessions by, forexample, monitoring the number of mobile devices 120 that are receivingWMBS content and monitor network conditions during the WMBS session. Forexample, BVPS 240 may monitor network congestion, network bandwidth,dates and times of the session, and whether the mobile devices 120 arelocated within WMBS service area 110. BVPS 240 may also, oralternatively, determine whether to provide a particular content item toone or more mobile devices 120 as a multicast or broadcast transmission,or to allow the content to be provided by unicast. BVPS 240 may alsoindicate the content that is currently being provided as well as contentthat may be of interest to users.

BMSC 250 may include one or more computation and/or communicationdevices, that gather, process, and/or provide information to facilitateWMBS communications. BMSC 250 may reserve bandwidth at WMBS service area110 (e.g., at base station 130) before a WMBS session begins, and mayreceive content data (e.g., multimedia) from CDN 150. BMSC 250 mayencode the received content data, perform forward error correction, andmodulate the data into symbols for transmission. BMSC 250 may multicastor broadcast content data to mobile devices 120 within WMBS service area110, when mobile device 120 requests the content data, and may terminatethe WMBS session after all of the content has been sent, or after apredetermined time period. ADF 250-1 may be part of BMSC 250, and maystore and manage the flow of symbols/data generated by BMSC for filerepair. ADF 250-1 may answer requests for file repair from mobile device120, and provide the data in the form of symbols in a unicast responseto mobile device 120.

FIG. 3 is a block diagram illustrating an exemplary Long Term Evolution(LTE) networking environment 300 according to an embodiment. LTEenvironment 300 may include an evolved packet core (EPC) 303, an evolvedUniversal Mobile Telecommunications System (UMTS) Terrestrial RadioAccess Network (eUTRAN) 305, and wide area network (WAN) 307. eUTRAN 305may further include one or more mobile devices, such as, for example,User Equipment (UEs) 365-1 and 365-2 (as used herein, plurally referredto as “UE 365” and individually as “UE 365-x”), and one or more basestations, such as, for example, eNodeBs 360. As described previously,UEs 365 may correspond to mobile devices 120. LTE networking environment300 may further include a WMBS system embodied as an eMBMS platform 341,which may include BVPS 240 and BMSC 250.

While environment 300 is shown in the context of an LTE network, itshould be appreciated that embodiments presented herein may operate inany appropriate wireless network(s). EUTRAN 305 and EPC 303 may furtherinclude one or more devices that are physical and/or logical entitiesinterconnected via standardized interfaces. EUTRAN 305 and EPC 303 mayprovide wireless packet-switched services and wireless Internet Protocol(IP) connectivity to mobile devices to provide, for example, data,voice, and/or multimedia services such as, for example, eMBMS. It isnoted that FIG. 3 depicts a representative environment 300 withexemplary components and configuration shown for purposes ofexplanation. Other embodiments may include additional or differentnetwork entities in alternative configurations than which areexemplified in FIG. 3.

Further referring to FIG. 3, EPC 303 may further include a servinggateway (SGW) device 312, a packet data network (PDN) gateway (PGW) 314,a Policy and Charging Rules Function (PCRF) 316, a mobility managemententity (MME) 318, a home subscriber server (HSS) 320, a MulticastCoordination Entity (MCE) 322, and an evolved Multimedia BroadcastMulticast System Gateway (eMBMS-GW) 324. It is noted that FIG. 3 depictsa representative EPC 303 with exemplary components and configurationshown for purposes of explanation. Other embodiments may includeadditional or different network entities in alternative configurationsthan which are exemplified in FIG. 3.

Further referring to FIG. 3, eNodeBs 360 may include one or more devicesand other components having functionality that allow UEs 365 to connectto eUTRAN 305 over an access network wireless channel 350. ENodeBs 360may interface with EPC 303 via a S1 interface, which may be split into acontrol plane S1-C interface 334 and a data plane S1-U interface 332.S1-C interface 334 may interface with MME 318. S1-C interface 334 may beimplemented, for example, with a protocol stack that includes a NetworkAccess Server (NAS) protocol and/or Stream Control Transmission Protocol(SCTP). S1-U interface 332 may interface with SGW 312 and may beimplemented, for example, using a General Packet Radio Service TunnelingProtocol User Plane (GTP-U). ENodeBs 360 may communicate amongthemselves via an X2 interface (not shown). The X2 interface may beimplemented, for example, with a protocol stack that includes an X2application protocol and SCTP.

For eMBMS functionality, eNodeBs 360 may connect to MCE 322 over an M2interface 335. The embodiment shown in FIG. 3 illustrates a “centralizedMCE architecture” where MCE 322 may be a logical entity that can bedeployed as a stand-alone physical entity, or collocated in anotherphysical entity in EPC 303. In another embodiment (not shown), the EPC303 may be realized using a “distributed MCE architecture” where asingle MCE 322 is included in each eNodeB 360. MCE 322 may provide eMBMSsession control signaling over M2 interface 335 using SCTP, where eMBMSsession control signaling may include radio configuration data formulti-cell transmission modes. EnodeBs 360 may further communicate witheMBMS-GW 324 over an M1 interface 330, and send (i.e., broadcast ormulticast) eMBMS packets to each eNodeB 360 which is transmitting dataassociated with the service. M1 330 interface may be a user planeinterface for providing eMBMS traffic that can be implemented using theeMBMS synchronization protocol (SYNC) and GTP-U. The SYNC protocol helpseNodeBs 365 identify the timing for eMBMS radio frame transmission anddetect packet loss.

UEs 356 may exchange data with eNodeB 360 over access network wirelesschannel 350 which may provide both unicast, multicast and broadcastconnections over a standard LTE air interface. UEs 365 may alsoindependently exchange data with each other over a peer to peer wirelessnetwork 355. Peer to peer wireless network 355 may be any type ofwireless interface that may include, for example, any type of Wi-Fi(e.g., any IEEE 801.11x network, where x=a, b, c, g, and/or n). The peerto peer network may also include Bluetooth, a PC-5 interface, or anyother type of wireless communications protocol. In an embodiment, peerto peer wireless network 355 may be supported by a wide area wirelessnetwork may include any type wireless network covering larger areas, forexample a mesh network (e.g., IEEE 801.11s) and/or or a WiMAX IEEE802.16.

SGW 312 may provide an access point to and from UEs 365, may handleforwarding of data packets for UEs 365, and may act as a local anchorpoint during handover procedures between eNodeBs 360. SGW 312 mayinterface with PGW 314 through an S5/S8 interface 342. S5/S8 interface342 may be implemented, for example, using GTP-U.

PGW 314 may function as a gateway to WAN 307 through a SGi interface346. WAN 307 may include, for example, an IP Multimedia Subsystem (IMS)network, which may provide voice and multimedia services to UE 365,based on Session Initiation Protocol (SIP). A particular UE 365, whileconnected to a single SGW 312, may be connected to multiple PGWs 314,one for each packet network with which UE 365 communicates.

PCRF 316 provides policy control decision and flow based chargingcontrol functionalities. PCRF 316 may provide network control regardingservice data flow detection, gating, Quality of Service (QoS) and flowbased charging, etc. PCRF 316 may determine how a certain service dataflow shall be treated, and may ensure that user plane traffic mappingand treatment is in accordance with a user's subscription profile. PCRF316 may communicate with PGW 314 using a Gx interface 344. Gx interface344 may be implemented, for example, using a Diameter protocol.

MME 318 may implement control plane processing for EPC 303 and eUTRAN305. For example, MME 318 may implement tracking and paging proceduresfor UEs 365, may activate and deactivate bearers for UEs 365, mayauthenticate users of UEs 365, and may interface to non-LTE radio accessnetworks. MME 318 may also select a particular SGW 312 for a particularUE 365-x. MME 318 may interface with other MMEs (not shown) in EPC 303and may send and receive information associated with UEs 365, which mayallow MME 318 to take over control plane processing of UEs 365 servicedby another MME device, if the other MME device becomes unavailable. MME318 may communicate with SGW 312 through an S11 interface 338. S11interface 338 may be implemented, for example, using General PacketRadio Tunneling Protocol Control plane (GTPv2-C). S11 interface 338 maybe used to create and manage a new session for a particular UE 365-x.S11 interface 338 may be activated when MME 318 needs to communicatewith SGW 312, such as when the particular UE 365 attaches to EPC 303,when bearers need to be added or modified for an existing session forthe particular UE 365, when a connection to a new PGW 314 needs tocreated, or during a handover procedure (e.g., when the particular UE365-x needs to switch to a different SGW 312).

HSS device 320 may store information associated with UEs 365 and/orinformation associated with users of UEs 365. For example, HSS device320 may store user profiles that include authentication and accessauthorization information. MME 318 may communicate with HSS device 320through an S6a interface 340. S6a interface 340 may be implemented, forexample, using a Diameter protocol.

MCE 322 can be a separate entity as shown in FIG. 3 or be included aspart of each eNodeB 360. MCE 322 may provide admission control througheMBMS session control signaling and allocate wireless channel resourcesfor UEs 365 in an eMBMS area associated with eUTRAN 305. Specifically,MCE 322 may: 1) allocate time and frequency radio resources for eMBMStransmissions; and 2) determine radio configuration, such as, forexample, the Modulation and Coding Scheme (MCS) for eMBMS transmissionsby eNodeBs 360. MCE 322 may also be connected with MME 318 over an M3interface 336 to provide eMBMS session control signaling (e.g., “eMBMSSession Start” and “eMBMS Session Stop” commands) on an eUTRAN RadioAccess Bearer (E-RAB) level (i.e., no radio configuration data isconveyed). Exchanges over the M3 interface 336 may performed using SCTP.

eMBMS-GW 324 may distribute (i.e., multicast and/or broadcast) eMBMSuser plane data packets to eNodeBs 360 that participate in a eMBMS in aneMBMS area 110. The data packets may be distributed to participatingeNodeBs 360 using Internet Protocol (IP) Multicast. eMBMS-GW 324 mayreceive the eMBMS data packets (e.g., content streams) from CDN 150 viaBMSC 250 through WAN 307. The eMBMS data packets may be provided toeMBMS-GW 324 over an SGi-mb interface 348. eMBMS-GW 324 may alsoexchange eMBMS session control signaling (e.g., sessionstart/update/stop messages) with BMSC 250 over an SG-mb interface 349.The eMBMS session control signaling received from BMSC 250 may beforwarded to MCE 322 over an Sm interface 352, which are in turnforwarded towards the eUTRAN 305 through MME 318. Sm interface 352 maybe implemented using a GTPv2-C message protocol which may be carriedover User Datagram Protocol (UDP) to start, stop, and modify eMBMSsessions. eMBMS-GW 324 may be a logical entity that exists as a separatedevice or may be collocated in another device within EPC 303.

eMBMS platform 341 may receive files from CDN 150 via WAN 307 andprovide them ePC 303, where files may be efficiently distributed to UEs365 120 an eMBMS service area via multicast or broadcast. BMSC 250 mayact as gateway between content providers (e.g., CDN 150) and eMBMS-GW324 in EPC 303. BMSC 250 may receive content streams from contentproviders over wide area network 307 via, for example, an Ethernetconnection implementing TCP/IP. As noted above in the description ofFIG. 2, BMSC 250 may process the received data to facilitate itsdistribution as eMBMS packets by EPC 303, and perform bearer processingwhich may include adding forward error correction and preparing thereceived data for unidirectional delivery of files using the FileDelivery over Unidirectional Transport (FLUTE) protocol. BMSC 250 mayalso control and schedule the eMBMS sessions by providing sessioncontrol messages to eMBMS-GW over SGmb interface 349. The sessioncontrol messages may include service announcements, session start andstop messages, etc. BMSC 250 may also provide admission control for theeMBMS services by providing session membership, user authorization andauthentication, and security. CDN 150 and/or BMSC 250 may interface withWAN 307 using an Ethernet connection over TCP/IP, where the physicalinterfaces may be any interface having sufficient resources to supportthe exchange of traffic alerts and traffic notifications. Suchinterfaces may include, for example, 10BASE-T, 1000BASE-TX, and/or1000BASE-T over twisted pair, coaxial cable, and/or optical fiber.

Wide Area Network 307 may be part of back end network(s) 230-2, andinclude any type wired or wireless network covering larger areas. Forexample, WAN 307 may include a metropolitan area network (MAN), a PublicSwitched Telephone Network (PSTN), an ad hoc network, an intranet, theInternet, a fiber optic-based network, a wireless network, and/or acombination of these or other types of networks. WAN 307 may be an IPbased network or utilize Multi-Protocol Label Switching (MPLS), and mayinclude a mesh network (e.g., IEEE 801.11s) and/or or a WiMAX IEEE802.16. WAN 307 may include one or more circuit-switched networks and/orpacket-switched networks.

FIG. 3 depicts a representative environment 300 with exemplarycomponents and configuration and is shown for purposes of explanation.Other implementations may include fewer components, differentcomponents, differently arranged components, or additional componentsthan exemplified in FIG. 3.

FIG. 4 is a block diagram showing exemplary components of a UE 365according to an embodiment. UE 365 may include any mobile communicationdevice configured to communicate with access network(s) 230-1 (e.g.,eUTRAN 305) via wireless signals. UE 365 may include a bus 410, aprocessor 415, memory 420, a read only memory (ROM) 425, a storagedevice 430, one or more input device(s) 435, one or more outputdevice(s) 440, a wireless interface 445, a navigation system 455, and amodem 457. Bus 410 may include a path that permits communication amongthe elements of UE 365.

Processor 415 may include a processor, microprocessor, or processinglogic that may interpret and execute instructions. Memory 420 mayinclude a random access memory (RAM) or another type of dynamic storagedevice that may store information and instructions for execution byprocessor 415. In an embodiment, instructions/software corresponding toMCM-MW 215 and/or repair manager 217 may be stored in memory 420. Inother embodiments, instructions may also be stored, in whole, or inpart, in ROM 425 and/or storage device 430 in addition to memory 420.MCM-MW 215 may control modem 457 to facilitate selection and reception,via access network wireless channel 350, of the broadcast and/ormulticast, and provide functionality for unicast file repair of WMBSreceived content via access network wireless channel 350. The unicastfile repair techniques may include, for example, the conventional filerepair and/or byte range file repair presented in the discussion of FIG.1B. Repair manager 217 may operate in conjunction with MCM-MW 215, whererepair manager 217 facilitates file repair between UEs 365 over peer topeer wireless network 355.

ROM 425 may include a ROM device or another type of static storagedevice that may store static information and instructions for use byprocessor 415. Storage device 430 may include erasable solid state,magnetic and/or optical recording medium and its corresponding drive tostore data and/or processor instructions when UE 365 is unpowered or ina power saving mode (e.g., a sleep state). Storage device 430 mayinclude, for example, secure digital (SD) card, flash memory within UE365, etc.

Input device(s) 435 may include one or more mechanisms that permit anoperator to input information to UE 365, such as, for example, a keypador a keyboard, a microphone, voice recognition, a touchscreen, and/orbiometric mechanisms, etc. Output device(s) 440 may include one or moremechanisms that output information to the operator, including a display,a speaker, etc. Wireless interface 445 may include any transceivermechanism that enables UE 365 to communicate with other devices and/orsystems. For example, wireless interface 445 may include mechanisms forcommunicating with another device or system via a network, such aswireless network eUTRAN 305 via access network wireless channel 350.Additionally, wireless interface 445 permits UE 365 to receive WMBSsession content. Wireless interface 455 may also provide mechanisms forcommunicating with other mobile devices 120 over peer to peer wirelessnetwork 355.

Navigation system 455 may be any system that provides position data inan absolute reference (e.g., a satellite navigation system (SNS)receiver providing position data in the WGS-84 system) and/or relativereference(s) (e.g., accelerometers). When deriving positions, navigationsystem 455 may utilize a receiver specifically designed for use with theSNS that extracts position, using conventional techniques, from aplurality of signals transmitted by SNS satellites. Various SNS may beused, which typically include a system of transmitters positioned toenable mobile devices 120 to determine its location based on signalsreceived from the transmitters. In a particular example, suchtransmitters may be located on Earth orbiting satellites. For example, asatellite in a constellation of Global Navigation System (GNS) such asGlobal Positioning System (GPS), Galileo, or Glonass may transmit asignal marked with a Pseudorandom Noise (PN) code that may bedistinguishable from PN codes transmitted by other satellites in theconstellation.

Modem 457 may facilitate signaling and coordination with networkelements in EPC 303 for exchanging data via networks 230. Modem 457 maybe a baseband processor that manages network protocols (e.g., WMBS),radio control functions, including signal modulation/demodulation,encoding, frequency shifting, etc., Modem 457 may thus facilitate bothaccess stratum and non-access stratum functionality.

UE 365 may transfer messages and/or perform certain operations orprocesses, as described in detail below in reference to FIGS. 5-8. UE365 may perform these operations in response to processor 415 executingsoftware instructions contained in a computer-readable medium, such asmemory 420. A computer-readable medium may be defined as a physical orlogical memory device. A logical memory device may include memory spacewithin a single physical memory device or spread across multiplephysical memory devices. The software instructions may be read intomemory 420 from another computer-readable medium, such as storage device430, or from another device via wireless interface 445. The softwareinstructions contained in memory 420 may cause processor 415 to performoperations or processes that will be described in detail with respect toFIG. 8. Alternatively, hardwired circuitry may be used in place of or incombination with software instructions to implement processes consistentwith the principles of the embodiments. Thus, exemplary implementationsare not limited to any specific combination of hardware circuitry andsoftware. The configuration of components of UE 365 illustrated in FIG.4 is for illustrative purposes only. It should be understood that otherconfigurations may be implemented. Therefore, UE 365 may includeadditional, fewer and/or different components than those depicted inFIG. 4.

FIG. 5 is a flow diagram 500 showing exemplary process blocks and signalflows for initiating a file repair via a wireless peer to peer network355. For ease of explanation, the process blocks and signal flows inFIG. 5 are primarily shown with respect to mobile device 120-1; however,given the nature of peer to peer networks, any/all mobile devices 120may perform the process blocks and message exchanges to initiate a filerepair via wireless peer to peer network 355. Initially, MCM-MW 215 inmobile device 120-1 may monitor the file size and bandwidth whilereceiving data from base station 130 via a WMBS session (Block 505).MCM-MW 215 may then calculate an end time of the WMBS session (Block510). MCM-MW 215 may then send information regarding the on-going WMBSsession to repair manager 217, also residing in mobile device 120-1(Message 502). Message 502 may include file size, received number ofblocks, WMBS session bandwidth, and/or other parameters characterizingthe ongoing WMBS session. MCM-MW 215 may then monitor blocks received bybase station 130 via the WMBS session, generate progress notifications(Block 515)., and send progress notifications to repair manager (Message504). Upon receiving Message 502 and Message 504, repair manager 217 mayperform a second calculation of the WMBS session end time based on thefile size and the received blocks, as a verification of the end timecalculated by MCM-MW 215 in Block 510 (Block 520). The end timecalculated by repair manager 217 may be more accurate than the end timecalculated by MCM-MW 215. Alternatively, repair manager 217 may computethe WMBS session end time by monitoring progress notifications providedin Message 504. Based on the computed end time, repair manager 217 maydetect when WMBS session has completed (Block 525). Upon detectingcompletion, repair manager 217 may broadcast a completion message viawireless peer to peer network 355 to peer mobile devices 120-2 through120-5 (Message 506). The completion message may identify the sendingmobile device 120, the file received during the WMBS session from basestation 130, and the download status of the file (e.g., the amount ofthe file received as a fraction and/or absolute number of bytes, blocks,etc.). Upon receiving the completion message, peer mobile devices 120-2through 120-5 may compare their progress with respect to receiving thefile during the WMBS session to the received broadcast completionmessage (BCM) from mobile device 120-1 (Block 530).

In a similar manner, once all of the mobile devices 120 have exchangedbroadcast completion messages and have compared their respectiveprogress (e.g., completion of the WMBS session), mobile devices 120 maydetermine which mobile devices 120 received the entire file, or if noneof the devices received the entire file, which device received thelargest amount of the file via the WMBS session (Blocks 535A and 535B).The mobile device(s) 120 having the entire file may become seed mobiledevices, which is discussed further in reference to FIG. 6. If none ofthe mobile device(s) 120 received 100% of the file, the mobile devicereceiving the largest amount of the file may be designated as a leadmobile device, which is discussed further in reference to FIG. 7.

FIG. 6 is a flow diagram 600 showing exemplary process blocks and signalflows for performing a seed mode file repair via a wireless peer to peernetwork 355. As in FIG. 5, for ease of explanation, the process blocksand signal flows in FIG. 6 are primarily shown with respect to mobiledevice 120-1 which, in the example shown in FIG. 6, has been designateda seed mobile device. However, given the nature of peer to peernetworks, any or all mobile devices 120 may perform the process blocksand message exchanges to perform seed mode file repair via wireless peerto peer network 355.

Initially, repair manager 217 within seed mobile device 120-1 maygenerate a list of available peer mobile devices 120-2 through 120-5that may exchange data with seed mobile device 120-1 over wireless peerto peer network 355 (Block 605). Once the list is generated, seed mobiledevice 120-1 may execute a sort algorithm generating a priority queue ofpeer mobile devices 120-2 through 120-5 (Block 610). The priority queueis sorted to establish the order of peer mobile devices 120-2 through120-5 in which seed mode file repair will take place. An algorithmexecuting on seed mode device 120-1 may prioritize peer mobile devices120-2 through 120-5 based on the amount of the file received during theWMBS session, the signal strength associated with each peer mobiledevice 120-2 through 120-5, and/or a relative importance of a particularpeer mobile device 120 (e.g., based on service agreement quality ofservice). Once the priority queue is generated, seed mobile device 120-1may broadcast the priority queue to peer mobile devices 120-2 through120-5 via wireless peer to peer network 355 (Message 602). Transmittingthe priority queue enables peer devices 120-2 through 120-5 to be awareof the queue priority. The priority queue may be recomputed in anongoing and real-time basis during the seed mode file repair to accountfor changes in peer mobile device 120-2 through 120-5, such as changesin position, changes in signal strength, etc. In some instances, a peermobile device 120-x may increase signal strength to increase priority inthe priority queue based on user preferences and/or command, thevelocity of the peer mobile device 120-x, and/or quality of servicerequirements based on a service agreement.

Seed mobile device 120-1 may then establish a maximum number ofsimultaneous connections that may be made with peer mobile devices 120-2through 120-5 over wireless peer to peer network 355 (Block 615). Themaximum number of simultaneous connections may be determined as aconfigurable parameter (by the user or the network operator). Seedmobile device 120-1 may then send repair data to peer mobile devices120-2 through 120-5 based on the priority queue (Message 604). As eachpeer mobile device 120-x reaches 100% (entire file is stored) and isfully repaired, peer mobile device 120-x transition into seed mode andsupply other peer mobile devices 120 as needed (Block 620). Seed mobiledevice 120-1 may transition out of seed mode after a predeterminednumber of file repairs are completed so as to not overload seed mobiledevice 120-1.

FIG. 7 is a flow diagram 700 showing exemplary process blocks and signalflows for performing a lead mode file repair via a wireless peer to peernetwork 355. As in FIG. 6, for ease of explanation, the process blocksand signal flows in FIG. 7 are primarily shown with respect to mobiledevice 120-1; however, given the nature of peer to peer networks, allmobile devices 120 may perform the process blocks and message exchangesto perform lead mode file repair via wireless peer to peer network 355.As noted above, if none of the mobile devices 120 received 100% of thefile, a particular mobile device 120-j may be selected by mobile devices120 as a lead mobile device. The lead mobile device may be selectedbased on having the largest amount of the file received by the WMBSsession, the greatest signal strength with access network wirelesschannel 350, and/or the location and/or velocity of the mobile device120-j, etc. In the embodiment shown in FIG. 7, assume that mobile device120-1 is designated as a lead mobile device.

Further referring to FIG. 7, repair manager 217 may send a message toinstruct MCM-MW 215 to enter lead mode file repair (Message 702). MCM-MW215 may then transmit a unicast repair request to CDN 150 or BMSC 250(Message 704). If byte range file repair is desired, message 704 may besent to CDN 150. If conventional file repair is desired, message 704 maybe sent to BMSC 250. The selection of where to send message 704 maydepend upon settings in lead mobile device 120-1, and/or which networkdevice (CDN 150 or BMSC 250) has the repair data available. Once theunicast repair request is processed, CDN 150 or BMSC 250 may providerepair data to MCM-MW 215 through a unicast connection over accessnetwork wireless channel 350 (Message 706). MCM-MW 215 may monitor theunicast connection to determine when the transmission of file repairdata is complete (Block 705). MCM-MW 215 may notify repair manager 217once the unicast transmission of repair data is complete by sending arepair status message to repair manager 217 (Message 708).

Repair manager 217 within lead mobile device 120-1 may transition toseed mode by generating a list of available peer mobile devices 120-2through 120-5 that may exchange data with seed mobile device 120-1 overwireless peer to peer network 355 (Block 710). Once the list isgenerated, lead mobile device 120-1 may execute a sort algorithm andgenerate a priority queue of peer mobile devices 120-2 through 120-5(Block 715). The priority queue is sorted to establish the order of peermobile devices 120-2 through 120-5 in which seed mode file repair willtake place. An algorithm executing on lead mode device 120-1 mayprioritize peer mobile devices 120-2 through 120-5 based on the amountof the file received during the WMBS session, the signal strengthassociated with each peer mobile device 120-2 through 120-5, and/or arelative importance of a particular peer mobile device 120 (e.g., basedon service agreement quality of service). Once the priority queue isgenerated, lead mobile device 120-1 may broadcast the priority queue topeer mobile devices 120-2 through 120-5 via wireless peer to peernetwork 355 (M708). The priority queue is sent so that peer devices120-2 through 120-5 are aware of the queue priority. The priority queuemay be recomputed in an ongoing real-time basis during the seed modefile repair to account for changes in peer mobile device 120-2 through120-5 such as changes in position, signal strength, etc. In someinstances, a peer mobile device 120-x may increase signal strength toincrease priority in the priority queue based on user preferences and/orcommand, the velocity of the peer mobile device 120-x, and/or quality ofservice requirements based on a service agreement).

Lead mobile device 120-1 may then establish a maximum number ofsimultaneous connections that may be made with peer mobile devices 120-2through 120-5 over wireless peer to peer network 355 (Block 720). Themaximum number of simultaneous connections may be determined as aconfigurable parameter (by the user or the network operator). Seedmobile device 120-1 may then send repair data to peer mobile devices120-2 through 120-5 based on the priority queue (M710). As each peermobile device 120-x reaches 100% (e.g., stores the entire file) and isfully repaired, peer mobile device 120-x transition into seed mode andsupply other peer mobile devices 120 as needed (Block 725). Lead mobiledevice 120-1 may transition out of seed mode after a predeterminednumber of file repairs are completed so as to not overload lead mobiledevice 120-1.

FIG. 8 is a flow chart showing an exemplary process 800 for repairingWMBS session data via a peer to peer network. Process 800 may beperformed by mobile device 120-1 for example, by executing instructionsstored in memory 420 on processor 415. Mobile device 120-1 may initiallyreceive at least a part of a file transmitted by the WMBS session viaaccess network wireless channel 350, where the WMBS session alsotransmits at least parts of the file to peer mobile devices 120-2through 120-5 via access network wireless channel 350 (Block 810).

Mobile device 120-1 may then exchange, via peer to peer wireless network355, completion messages with and peer mobile devices 120-2 through120-5 upon completion of the WMBS session (Block 820). In an embodiment,exchanging completion messages may further cause mobile device 120 tomonitor a file size and/or broadcast bandwidth associated with the WMBSsession. Mobile device 120-1 may then calculate, based on themonitoring, an end time of the WMBS session, and generate progressnotifications by monitoring received data blocks. Mobile device 120-1may then generate the completion message, which may identify the sendingdevice, information regarding the file received (e.g., file name,version, hash value, meta data, etc.) via the WMBS session, and theamount of the file received by mobile device 120-1. In anotherembodiment, mobile device 120-1 may verify, the calculated end time,which may further cause mobile device 120-1 to determine the number ofreceived blocks and recalculate the end time based on the receivedblocks and a total file size.

Mobile device 120-1 may determine the amount of the file received viathe WMBS session at mobile device 120-1, and also determine the amountsof the file received at each peer mobile devices 120-2 through 120-5based on the exchanged completion messages (Block 830).

Mobile device 120-1 may determine whether it received the entire filevia the access network wireless channel 350 during the WMBS session(Block 840).

If mobile device 120-1 received the entire file, then mobile device120-1 may enter seed mode file repair, and send file repair data via thepeer to peer wireless network 355 to a group of peer mobile devices120-2 through 120-5 identified as receiving amounts less than the entirefile (Block 850). In an embodiment, mobile device 120-1 may establish anumber of simultaneous connections with peer mobile devices 120-2through 120-5, where the number of simultaneous connections is aconfigurable parameter. In another embodiment, mobile device 120-1 maygenerate a prioritized queue of the peer UE devices 120-2 through 120-5,and provide the prioritized queue to each of peer mobile devices 120-2through 120-5. Mobile device 120-1 may then send data to repair the fileon each of peer mobile devices 120-2 through 120-5 based on theprioritized queue. In an embodiment, mobile device 120-1 may generatethe prioritized list by sorting the peer mobile devices 120-2 through120-5 based on at least one of device to device signal strength, oramounts of the file received by each of the plurality of peer mobiledevices 120-2 through 120-5.

If, in Block 840, mobile device 120-1 does not receive the entire fileduring the WMBS session via access network wireless channel 350 (Block840-N), mobile device 120-1 may determine whether the amount of the filereceived is greater than the amounts of the files received by each ofpeer mobile devices 120-2 through 120-5 (Block 860). If, in Block 860,mobile device 120-1 determines the amount of the file received is notgreater than the amounts of the files received by each of peer mobiledevices 120-2 through 120-5 (Block 860-N), mobile device 120-1 may waitfor repair data to be sent via peer to peer wireless network 355 fromone of the peer mobile devices 120-2 through 120-5 having received afile which is larger than other mobile devices 120 (Block 870).

If, in Block 860, mobile device 120-1 determines the amount of the filereceived is greater than the amounts of the files received by each ofpeer mobile devices 120-2 through 120-5 (Block 860-Y), mobile device120-1 will establish a connection to access network 230-1 to obtain filerepair data through a unicast session via access network wirelesschannel 350 (Block 880). In an embodiment, mobile device 120-1 mayconnect to CDN 150 via the access network wireless channel 350, andrequest data to repair the file on mobile device 120-1 based on abyte-range file repair procedure. In another embodiment, mobile device120-1 may connect to WMBS platform 140 multicast platform via accessnetwork wireless channel 350, and request data to repair the file on UEdevice 120-1 based a conventional file repair procedure.

Once mobile device 120-1 receives the repair data to complete the file,mobile device 120-1 may transition into seed mode by sending file repairdata, via peer to peer wireless network 355, to peer mobile devices120-2 through 120-5 for repairing the files on each of the peer mobiledevices 120-2 through 120-5 (Block 890).

Embodiments for repairing files using peer to peer networks may beapplicable to a variety of environments where a group of mobile devicesreceive data through WMBS services. For example, WMBS services may beused to broadcast large amounts of data (e.g., 6 Gigabytes of videocontent) each evening to a cluster of tablet devices which may beembedded in golf carts. Conventional approaches for repairing the videocontent on the tablet devices may utilize 200 simultaneous unicastconnections requests, which may disrupt the network. Having the tabletsrepair the video content over a peer to peer network preventsoverloading the wireless network and saves operational costs. In anotherembodiment, large groups automobiles may have firmware updates appliedat ports of entry as they are being moved off transport ships. Thus,there may be tens of thousands of automobiles waiting in a queue as partof the transport logistic process. WMBS sessions are an efficientapproach to update firmware in the vehicles, and peer to peer filerepair can ensure that each vehicle will receive a complete firmwareupdate in an efficient and cost-effective manner. In another embodiment,firmware over the air (FOTA) updates for enterprise devices, such ascash registers, digital signs, appliances, taxi/transit vehicles,traffic cameras, etc., may be provided over WMBS sessions. Repairingfirmware files using a peer to peer network between the enterprisedevices can avoid large clusters of devices choking the network withsimultaneous unicast repair requests.

The foregoing description of implementations provides illustration anddescription, but is not intended to be exhaustive or to limit theinvention to the precise form disclosed. Modifications and variationsare possible in light of the above teachings or may be acquired frompractice of the invention. For example, while series of messages and/orblocks have been described with regard to FIGS. 5-8, the order of themessages and/or blocks may be modified in other embodiments. Further,non-dependent messaging and/or processing blocks may be performed inparallel.

Certain features described above may be implemented as “logic” or a“unit” that performs one or more functions. This logic or unit mayinclude hardware, such as one or more processors, microprocessors,application specific integrated circuits, or field programmable gatearrays, software, or a combination of hardware and software.

In the preceding specification, various preferred embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded inan illustrative rather than restrictive sense.

To the extent the aforementioned embodiments collect, store or employpersonal information of individuals, it should be understood that suchinformation shall be collected, stored, and used in accordance with allapplicable laws concerning protection of personal information.Additionally, the collection, storage and use of such information can besubject to consent of the individual to such activity, for example,through well known “opt-in” or “opt-out” processes as can be appropriatefor the situation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

The terms “comprises” and/or “comprising,” as used herein specify thepresence of stated features, integers, steps or components but does notpreclude the presence or addition of one or more other features,integers, steps, components, or groups thereof. Further, the term“exemplary” (e.g., “exemplary embodiment,” “exemplary configuration,”etc.) means “as an example” and does not mean “preferred,” “best,” orlikewise.

No element, act, or instruction used in the description of the presentapplication should be construed as critical or essential to theinvention unless explicitly described as such. Also, as used herein, thearticle “a” is intended to include one or more items. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, at a userequipment (UE) device, at least a part of a file transmitted by awireless multicast/broadcast service (WMBS) session via an accessnetwork, wherein the WMBS session also transmits at least parts of thefile to a plurality of peer UE devices via the access network;exchanging, via a peer to peer network, completion messages between theUE device and the plurality of peer UE devices upon completion of theWMBS session; identifying, at the UE device, an amount of the filereceived at the UE device, and amounts of the file received at each ofthe plurality of peer UE devices based on the exchanged completionmessages; sending data, via the peer to peer network from the UE deviceto a group of peer UE devices identified as receiving amounts less thanthe entire file, to repair the file on each of the group of peer UEdevices, in response to identifying that the UE device received theentire file; and obtaining data, via the access network, to repair thefile on the UE device in response to identifying that the UE devicereceived less than the entire file and receive more of the file thaneach of the group of peer UE devices, and sending data, via the peer topeer network, of the repaired file from the UE device to the group ofpeer UE devices to repair the file on each of the group of peer UEdevices.
 2. The method of claim 1, wherein exchanging completionmessages further comprises: monitoring, at the UE device, at least oneof file size or broadcast bandwidth associated with the WMBS session;calculating, at the UE device based on the monitoring, an end time ofthe WMBS session; generating, by the UE device, progress notificationsby monitoring received data blocks; and generating, at the UE device,the completion message, wherein the completion message identifies asending UE device, the file received via the WMBS session, and theamount of the file received by the UE device.
 3. The method of claim 2,further comprising: verifying, at the UE device, the calculated endtime, wherein the verifying further comprises: determining the number ofreceived blocks; and recalculating the end time based on the receivedblocks and a total file size.
 4. The method of claim 1, wherein sendingdata from the UE device to the group of peer UE devices furthercomprises: establishing, by the UE device, a number of simultaneousconnections with the peer UE devices, wherein the number of simultaneousconnections is a configurable parameter.
 5. The method of claim 1,wherein sending data from the UE device to the group of peer UE devicescomprises: generating, at the UE device, a prioritized queue of thegroup of peer UE devices; providing, from the UE device, the prioritizedqueue to each of the group of peer UE devices; and sending, from the UEdevice, data to repair the file on each of the group of peer UE devicesbased on the prioritized queue.
 6. The method of claim 5, whereingenerating the prioritized queue further comprises: sorting the group ofpeer UE devices based on at least one of device to device signalstrength, or amounts of the file received by each of the plurality ofthe group of peer UE devices.
 7. The method of claim 1, whereinobtaining data from the network to repair the file on the UE devicefurther comprises: determining that the UE device received a greateramount of the file than any of the group of peer UE devices; andestablishing a connection to the access network to receive data torepair the file on the UE device.
 8. The method of claim 7, whereinestablishing a connection further comprises: connecting to a contentdelivery network via the access network; and requesting data to repairthe file on the UE device based on a byte range repair procedure.
 9. Themethod of claim 7, wherein establishing a connection further comprises:connecting to a multicast platform via the access network; andrequesting data to repair the file on the UE device based on aconventional file repair procedure.
 10. A user equipment (UE) device,comprising: a wireless interface that communicates via an access networkand a peer to peer network; a memory configured to store instructions;and a processor, coupled to the wireless interface and the memory,wherein the processor is configured to execute the instructions storedin the memory to: receive at least a part of a file transmitted by awireless multicast/broadcast service (WMBS) session via the accessnetwork, wherein the WMBS session also transmits at least parts of thefile to a plurality of peer UE devices via the access network; exchange,via the peer to peer network, completion messages between the UE deviceand the plurality of peer UE devices upon completion of the WMBSsession; identify an amount of the file received at the UE device, andamounts of the file received at each of the plurality of peer UE devicesbased on the exchanged completion messages; send data, via the peer topeer network, to a group of peer UE devices identified as receivingamounts less than the entire file, to repair the file on each of thegroup of peer UE devices, in response to identifying that the UE devicereceived the entire file; and obtain data, via the access network, torepair the file on the UE device in response to identifying that the UEdevice received less than the entire file and receive more of the filethan each of the group of peer UE devices, and send data, via the peerto peer network, of the repaired file from the UE device to the group ofpeer UE devices to repair the file on each of the group of peer UEdevices.
 11. The UE device of claim 10, wherein the instructions toexchange completion messages further causes the processor to: monitor atleast one of file size or broadcast bandwidth associated with the WMBSsession; calculate, based on the monitoring, an end time of the WMBSsession; generate progress notifications by monitoring received datablocks; and generate the completion message, wherein the completionmessage identifies a sending UE device, the file received via the WMBSsession, and the amount of the file received by the UE device.
 12. TheUE device of claim 11, further comprising instructions to cause theprocessor to verify the calculated end time, wherein the instructions toverify cause the processor to: determine the number of received blocks;and recalculate the end time based on the received blocks and a totalfile size.
 13. The UE device of claim 10 wherein the instructions tosend data from the UE device to the group of peer UE devices furthercause the processor to: establish a number of simultaneous connectionswith the peer UE devices, wherein the number of simultaneous connectionsis a configurable parameter.
 14. The UE device of claim 10, wherein theinstructions to send data from the UE device to the group of peer UEdevices further cause the processor to: generate a prioritized queue ofthe group of peer UE devices; provide the prioritized queue to each ofthe group of peer UE devices; and send data to repair the file on eachof the group of peer UE devices based on the prioritized queue.
 15. TheUE device of claim 14, wherein the instructions to generate theprioritized queue further cause the processor to: sort the group of peerUE devices based on at least one of device to device signal strength, oramounts of the file received by each of the plurality of the group ofpeer UE devices.
 16. The UE device of claim 10, wherein the instructionsto obtain data from the network to repair the file on the UE devicefurther cause the processor to: determine that the UE device received agreater amount of the file than any of the group of peer UE devices; andestablish a connection to the access network to receive data to repairthe file on the UE device.
 17. The UE device of claim 16, wherein theinstructions to establish the connection further cause the processor to:connect to a content delivery network via the access network; andrequest data to repair the file on the UE device based on a byte-rangerepair procedure.
 18. The UE device of claim 16, wherein theinstructions to establish a connection further cause the processor to:connect to a multicast platform via the access network; and request datato repair the file on the UE device based a conventional file repairprocedure.
 19. A non-transitory computer readable medium comprisinginstructions, which, when executed by a processor, causes the processorto: receive, at a UE device, at least a part of a file transmitted by awireless multicast/broadcast service (WMBS) session via the accessnetwork, wherein the WMBS session also transmits at least parts of thefile to a plurality of peer UE devices via the access network; exchange,via a peer to peer network, completion messages between the UE deviceand the plurality of peer UE devices upon completion of the WMBSsession; identify, at the UE device, an amount of the file received atthe UE device, and amounts of the file received at each of the pluralityof peer UE devices based on the exchanged completion messages; senddata, via the peer to peer network, to a group of peer UE devicesidentified as receiving amounts less than the entire file, to repair thefile on each of the group of peer UE devices, in response to identifyingthat the UE device received the entire file; and obtain data, via theaccess network, to repair the file on the UE device in response toidentifying that the UE device received less than the entire file andreceived more of the file than each of the group of peer UE devices, andsend data, via the peer to peer network, of the repaired file from theUE device to the group of peer UE devices to repair the file on each ofthe group of peer UE devices.
 20. The non-transitory computer readablemedium of claim 19, wherein the instructions to exchange completionmessages further causes the processor to: monitor, at the UE device, atleast one of file size or broadcast bandwidth associated with the WMBSsession; calculate, at the UE device, based on the monitoring, an endtime of the WMBS session; generate, at the UE device, progressnotifications by monitoring received data blocks; and generate, at theUE device, the completion message, wherein the completion messageidentifies a sending UE device, the file received via the WMBS session,and the amount of the file received by the UE device.